UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

The SDN controller must be configured to separate tenant functionality from system management functionality.


Overview

Finding ID Version Rule ID IA Controls Severity
V-206738 SRG-NET-000512-SDN-001070 SV-206738r385561_rule Medium
Description
Network-as-a-Service (NaaS) is frequently offered in a multi-tenant paradigm, where customers share network infrastructure. SDN provides an approach to the provisioning of virtual network services by owners of the network infrastructures to third parties. This leads to various multi-tenancy deployments using different techniques, each of which provides different levels of control while requiring different types of isolation among users. For example, a southbound implementation allows multiple guest controllers sharing the same data forwarding elements; whereas a northbound implementation enables multiple guest applications sharing the whole SDN infrastructure including the SDN controller. To ensure stable network operations in a multi-tenant deployment, it is imperative that the SDN controller is configured to separate tenant functionality from system management functionality.
STIG Date
SDN Controller Security Requirements Guide 2024-05-28

Details

Check Text ( C-6995r363152_chk )
Review the SDN controller configuration to determine whether tenant functionality is separated from system management functionality using separated instances within the controller framework as well as Role-based access control (RBAC).

If the SDN controller is not configured to separate tenant functionality from system management functionality, this is a finding.
Fix Text (F-6995r363153_fix)
Configure the SDN controller to have tenant functionality separated from system management functionality using separated instances within the controller framework as well as Role-based access control (RBAC).